feat: comment on GitHub step summary #986
Conversation
|
@koozz Would you mind removing the dist files update so we can run the workflow tests on this change? :) It's a bit weird how this goes, but we optimized it so that changes that did nothing to our dist files were skipped. Which I at least think is why they are not triggered 😅 |
Sure one sec. |
Using the GitHub step summary feature, the Pulumi output can be stored on the GitHub step. This defeats the need to dive into the individual steps and find the Pulumi output. The input parameter comment-on-summary has the non-breaking default false. If true, then the action will add the results of the Pulumi action to the GitHub step summary. Signed-off-by: Jan van den Berg <koozz@linux.com>
koozz
force-pushed
the
master
branch
2 times, most recently
from
b8b90be
to
5c7a971
Compare
|
@simenandre I just disabled the workflows on my fork and dropped the automated commit from the PR. |
|
Hi @justinvp, please tag me if I need to change something else. |
|
Wow! Amazing feature. Would love to see this merged. |
|
Hi @simenandre, you added @justinvp but maybe there's someone else who can review and merge it? Kind regards and let me know if an update is required, |
Using the GitHub step summary feature, the Pulumi output can be stored on the GitHub step. This defeats the need to dive into the individual steps and find the Pulumi output.
The input parameter
comment-on-summaryhas the non-breaking defaultfalse. Iftrue, then the action will add the results of the Pulumi action to the GitHub step summary.Have tested it by referencing fork:
Showing the output in the Job summary:
Fixes: #761